home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d19
/
dlcnt157.arc
/
HISTORY.DLC
< prev
next >
Wrap
Text File
|
1991-01-26
|
10KB
|
213 lines
╔════════════════════════════════════════════════════╗
║ DLCounter - Written by Gary Bouchard ║
║ SysOp - The Computer Store BBS ║
║ St. Augustine, Florida (904)797-1713 ║
║ Copyright(c) 1990,91....All Rights Reserved ║
║ Released August 4, 1990 Modified January 24, 1991 ║
╚════════════════════════════════════════════════════╝
DLCounter History File in Reverse Order
- January 24, 1991 Ver 1.57
I added a feature that allows the user the define the minimum
download count to qualify for updating a DIR text record. The
default of course is 1, but a new keyword can be placed into the
configuration file along with the number the user chooses. The
keyword is "MIN_DLCOUNT". This is a different keyword from
MIN_DOWNLOAD, which is used in the BLT Display file generation.
Note the sample configuration enclosed in the zip file for the
explanation. A couple of cosmetic changes where made, and I
shortened the record length of the database file that is generated
by removing information that was not necessary. I am also working
on updating the documentation, which will follow the standard
established by others of being produced in WordPerfect 5.1 and will
be available to all users for a fee of $8.50 to cover the cost of
mailing and paper. This will be a professional style manual. I also
changed DLCDB (The debugging program) to follow the record format
produced by DLCount.
I also fixed that lingering problem of deleting the DIRxx.$$$
temporary work file if the user pressed the ESC key to abort
processing. DLCounter now correctly deletes this file, and ends.
I forgot to mention that a couple of versions ago, I fixed a
problem where DLCounter was not updating records if the filename
started with a non alphabetic symbol (i.e @,#,$,&,). I was looking
for A-Z or 1-9 for filenames in the first y
- December 27, 1990 Ver 1.56
Pat Monk reported a problem with DLCounter not processing the
DOWNLOAD.TXT file that had less than 30 or so records. The error
was a Divide by Zero error. That error was generated when
calculating the growth of the scale, and I had hardcoded the
formula, rather than put it into variable format. I tested the
correction by taking out all but one record from DOWNLOAD.TXT and
running the program, without a hitch. Turbo Pascal Version 6 now
has a Profiler program that will help me to optimize the code. I
will begin this once I receive my upgrade, so watch for updates. I
need to know if anyone is using the COUNT program that is included
in the ZIP file. COUNT is a standalone program that will create
your database file for you, if you have one too large for DLCOUNT
to handle because of memory. If I do not get any responses I will
discontinue that program. If you require assistance with the
program or have any suggestions you can call me at my voice line
(904)797-1713 or (800)424-4337.
- December 20, 1990 Ver 1.55
Ron Herrings previous report about not being able to process
conferences above 40 was true, but he had also reported that the
program would not process Directory File Listings greater than 39.
This again was because I had the upper limit of the array set to
40. I wasn't thinking about boards that might have more than 40 DIR
Files. This has been corrected. You will also notice that the "ß"
is gone from the version number. I figured that it has gone thru
enough beta testing, and is fairly stable now. I still do not have
my BBS up again yet, but you may still call me for support at the
number listed below. If you have any suggestions on what you would
like to see the program do, please let me know, and I'll try to
incorporate them in future releases. Updated documentation will be
put into the next maintenance release, so in the mean time please
consult the history file, docs and config files for operational
changes.
- September 18, 1990 Ver 1.54ß
Ron Herring reported that he could not process conferences above
40, which was quite true...I had the conference array set to a max
value of 40. No problem! I changed the array max to 100. If someone
needs more than this, please let me know. I also fixed the
positions that some of the secondary lines where ending up on if
they were not in the same place as the PIPE variable used in the
program. In other words, the program should put your secondary
lines exactly where you set them to be, rather than lining them up
with the PIPE variable that I was doing before. Sorry guys!
Due to financial difficulties, I find it necessary to temporarily
shut down my BBS until I get things caught up. Long Distance
charges can really drag you down sometimes. My voice number where
you can reach me during the day is 1-800-424-4337. This is in
Cincinatti, Ohio. Just ask for me. I cannot return calls, so if I
am not there, do not leave a message...please call back. I will
still support the DLCounter program via telephone until I can get
the BBS back up. I have been a PCBoard SysOp since version 10.0, so
I am not a fly by night board! If you have any difficulties with
the program, please call me, and I'll do my best to address them.
- September 11, 1990 Ver 1.53ß
Some problems reported from SysOps who do not necessarily use
position 32 of the secondary line for the start of the file
descriptions. Previously hardcoded, you may now specify what column
you wish the '|' symbol to be place in your file descriptions
secondary lines. If you recall, PCBoard uses this character as a
formatting guide in placing additional lines in file descriptions.
Pcboard does not show this character to the caller. In order to
specify your own column position, use the 'PIPE' variable in your
configuration file to tell DLCounter what column to place the '|'
(pipe symbol).
; Example;
PIPE 32
;
If the 'PIPE' command is not found in the configuration file the
program will default to column 32, as it always has. If you are
CHANGING the position, *FIRST* run DLCounter with the /CLEAR /NEW
command line switches to remove the previous DLCounter entries,
then change the 'PIPE' value, and re-run the program.
- September 8, 1990 Ver 1.52ß
In order to remain consistent with PCBoard(tm) macro conventions,
I have changed the program to look for the @USERCOUNT@ macro in
UPPER CASE characters. Please check your config files, and be sure
that you change the macro to upper case letters. Any further macros
added to the program in the future will be created in this fashion.
- September 4, 1990 Ver 1.51ß
A user reported that the program was adding extra lines to the
beginning of the DIRxx file if there was no header portion. I
checked that out, and sure enough!, Fixed...(I think!)..let me know
if you encounter any such circumstances.
- September 2, 1990 Ver 1.50ß
Note: Major revision change.
I added the capability for the user to define his/her own tagline
to be inserted into the DIRxx file. Within the configuration file
there is now a parameter called "USERSTRING". This parameter allows
you to assign a string of up to 40 characters to the variable, that
is inserted into the DIRxx file. The "USERSTRING" has a replaceable
macro type option that will allow you to define where in
"USERSTRING" you want your count to be. The replaceable macro
parameter is "@usercount@". Notice that the parameter is in lower
case letters...please define it that way in your USERSTRING or it
will not get replaced with the count in your DIRxx file listing. An
example would be like so;
USERSTRING Accessed: [@usercount@] Time(s)
-= OR =-
USERSTRING This file has been downloaded @usercount@ Times(s)
The "@" (at sign) surrounding the parameter is required, so that
the program may find the parameter within your USERSTRING. Do not
place quotes around the text unless you specifically want the quote
marks to show up in your DIRxx file entry. If you leave USERSTRING
blank, or leave it out of your configuration file, the program will
default to the standard entry that was present before;
Downloaded -> xx Time(s) .
I strongly recommend that if you change your USERSTRING tagline,
that you FIRST use the "/CLEAR /NEW" parameter to clear your
entries, so as not to cause any problems, then replace your
USERSTRING. I have arbitrarily changed the tagline several times in
testing with no ill effects, NOT using the "/CLEAR", because I use
the color highlighting, and the program looks for either the first
word on the line or the "@" character (which is part of the @X##
color macro) for reference.
Because of the way the line is checked for the update routine,
*DO NOT* place the @usercount@ as the first words on the line. If
you did, and this number was to change, it would no longer prove to
be a true match, and would insert ANOTHER line with the new count
rather than replacing the old one.
I also added a way to end the program besides Control break...If
you press the <ESC> Escape Key during operation, the program will
abort, and return you to the DOS prompt. Be aware that if you
abort, the temporary file DIRxx.$$$ will remain in your directory,
but the original DIRxx file will remain intact. You can also abort
the program during the creation of the Database file. I have not
updated the documentation with these recent improvements, but I
will when I get some time.. Keep an eye on this HISTORY file for
changes to the program.
Releases no longer supported are as follows;
- August 31, 1990 Ver 1.33ß
- August 29, 1990 Ver 1.32ß
- August 28, 1990 Ver 1.31ß
- August 27, 1990 Ver 1.30ß
- August 26, 1990 Ver 1.29ß
- August 25, 1990 Ver 1.28ß
- August 23, 1990 Ver 1.27ß
- August 22, 1990 Ver 1.26ß
- August 19, 1990 Ver 1.25ß
- August 18, 1990 Ver 1.24ß
- August 17, 1990 Ver 1.23ß
- August 15, 1990 Ver 1.22ß
- August 12, 1990 Ver 1.21ß
- August 9, 1990 Ver 1.10ß
- August 8, 1990 Ver 1.02ß
- August 6, 1990 Ver 1.01ß
- August 4, 1990 Ver 1.00ß
Initial release for wide beta testing.